What is google-p12-pem?
The google-p12-pem npm package is used to convert Google .p12 or PFX files to the PEM format. This is particularly useful when dealing with authentication in Google Cloud Platform services, as it allows developers to transform the private key obtained from Google into a format that can be used with various authentication libraries.
What are google-p12-pem's main functionalities?
Convert P12 to PEM
This feature allows you to convert a .p12 or PFX file to PEM format. The code sample demonstrates how to use the `getPem` function provided by the package to perform the conversion. The function takes the path to the .p12 file and a callback function that receives an error or the resulting PEM.
const { getPem } = require('google-p12-pem');
getPem('/path/to/key.p12', (err, pem) => {
if (err) {
console.error('Error converting P12 to PEM', err);
return;
}
console.log(pem);
});
Convert P12 to PEM with Promise
This feature is similar to the previous one but uses Promises instead of callbacks. It allows for better integration with modern asynchronous JavaScript code, such as async/await syntax.
const { getPem } = require('google-p12-pem');
getPem('/path/to/key.p12').then(pem => {
console.log(pem);
}).catch(err => {
console.error('Error converting P12 to PEM', err);
});
Other packages similar to google-p12-pem
node-forge
node-forge is a JavaScript implementation of various network security protocols. It includes functionality for creating, converting, and managing private keys and certificates in different formats, including PEM. It is more comprehensive than google-p12-pem, as it covers a wider range of cryptographic operations.
pem
pem is an npm package that provides a set of tools for managing and creating SSL certificates and keys. It can create private keys and CSRs, create certificates, read certificates, and more. It is similar to google-p12-pem in that it can handle PEM files, but it offers a broader set of features related to certificate management.
Convert Google .p12 keys to .pem keys.
A comprehensive list of changes in each version may be found in
the CHANGELOG.
Read more about the client libraries for Cloud APIs, including the older
Google APIs Client Libraries, in Client Libraries Explained.
Table of contents:
Quickstart
Installing the client library
npm install google-p12-pem
Using the client library
const {getPem} = require('google-p12-pem');
async function quickstart() {
const pem = await getPem(pathToCert);
console.log('The converted PEM:');
console.log(pem);
}
quickstart();
CLI style
gp12-pem myfile.p12 > output.pem
Samples
Samples are in the samples/
directory. Each sample's README.md
has instructions for running its sample.
The google-p12-pem Node.js Client API Reference documentation
also contains samples.
Supported Node.js Versions
Our client libraries follow the Node.js release schedule.
Libraries are compatible with all current active and maintenance versions of
Node.js.
If you are using an end-of-life version of Node.js, we recommend that you update
as soon as possible to an actively supported LTS version.
Google's client libraries support legacy versions of Node.js runtimes on a
best-efforts basis with the following warnings:
- Legacy versions are not tested in continuous integration.
- Some security patches and features cannot be backported.
- Dependencies cannot be kept up-to-date.
Client libraries targeting some end-of-life versions of Node.js are available, and
can be installed through npm dist-tags.
The dist-tags follow the naming convention legacy-(version)
.
For example, npm install google-p12-pem@legacy-8
installs client libraries
for versions compatible with Node.js 8.
Versioning
This library follows Semantic Versioning.
This library is considered to be General Availability (GA). This means it
is stable; the code surface will not change in backwards-incompatible ways
unless absolutely necessary (e.g. because of critical security issues) or with
an extensive deprecation period. Issues and requests against GA libraries
are addressed with the highest priority.
More Information: Google Cloud Platform Launch Stages
Contributing
Contributions welcome! See the Contributing Guide.
Please note that this README.md
, the samples/README.md
,
and a variety of configuration files in this repository (including .nycrc
and tsconfig.json
)
are generated from a central template. To edit one of these files, make an edit
to its templates in
directory.
License
Apache Version 2.0
See LICENSE